Forwarding multicast data packet

ABSTRACT

A method, device and system for forwarding a multicast data packet are provided. The system is an extended bridge constructed by a controlling bridge and a port extender. The controlling bridge transmits a multicast data packet with an ETAG having a multicast ECID via a cascade port, and the multicast ECID directs to egress ports in different VLANs of the multicast group on a port extender connected with the cascade port. The port extender receives the packet with the ETAG via an upstream port connected with the controlling bridge, searches for multicast duplication information matching the multicast ECID, duplicates the packet for each egress port based on the multicast duplication information, removes the ETAG of each copy of the packet, adds a port identification and a VLAN identification of each egress port to each copy of the packet, and transmits the packet containing the VLAN identification via each egress port.

CROSS REFERENCE TO RELATED APPLICATION

The present application is a National Phase of International ApplicationNumber PCT/CN2017/113553, filed Nov. 29, 2017, and claims priority toChinese Patent Application No. 201611086329.X entitled “METHOD, DEVICEAND SYSTEM FOR FORWARDING MULTICAST DATA PACKET” filed on Nov. 30, 2016,the entire content of which is incorporated herein by reference.

BACKGROUND

An Extended Bridge is constructed utilizing a Controlling Bridge (CB)and one or more Port Extenders (PE). The CB may be a single bridge or abridge constructed by a plurality of stacked bridges.

In one of prior multicast data packet forwarding methods utilized in theextended bridge, the CB may assign multiple multicast E-ChannelIdentifiers (ECIDs) to egress ports on a PE which belong to onemulticast group but different Virtual Local Area Networks (VLANs),duplicate multiple copies of a multicast data packet for the egressports in each VLAN, and add a VLAN tag and an ETAG to each copy of themulticast data packet. In each copy of the multicast data packet, themulticast ECID carried in the ETAG indicates the egress ports belongingto one VLAN corresponding to the VLAN tag. The CB may transmit themultiple copies of the multicast data packet carrying different the VLANtags and the different ETAGs to the PE via a cascade port. Based on eachcopy of the multicast data packets carrying a VLAN tag and a ETAG; thePE may duplicate one copy of the multicast data packet for each egressport corresponding to a multicast ECID of the ETAG, and transmit eachcopy of the multicast data packet with the ETAG removed therefrom viaeach egress port.

Based on the above method of forwarding a multicast data packet, theoccupied bandwidth of an E-stack link may be increased by transmitting aplurality of copies of the multicast data packet to the PE via thecascade port.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a flow diagram of a method of forwarding a multicastdata packet based on an example of the present disclosure.

FIG. 2 illustrates another flow diagram of a method of forwarding amulticast data packet based on an example of the present disclosure.

FIG. 3 illustrates a schematic diagram of forwarding a multicast datapacket by an extended bridge based on an example of the presentdisclosure.

FIG. 4 illustrates a schematic structure diagram of a device forforwarding a multicast data packet based on an example of the presentdisclosure.

FIG. 5 illustrates a schematic structure diagram of a controlling bridgeprovided with the device for forwarding a multicast data packet in FIG.4 based on an example of the present disclosure.

FIG. 6 illustrates a schematic structure diagram of a controlling bridgeprovided with the device for forwarding a multicast data packet in FIG.4 based on an example of the present disclosure.

FIG. 7 illustrates a schematic structure diagram of a device forforwarding a multicast data packet based on an example of the presentdisclosure.

FIG. 8 illustrates a schematic structure diagram of a port extenderprovided with the device for forwarding a multicast data packet in FIG.7 based on an example of the present disclosure.

FIG. 9 illustrates a schematic structure diagram of a port extenderprovided with the device for forwarding a multicast data packet in FIG.7 based on an example of the present disclosure.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The technical solutions of examples of the present disclosure will bedescribed clearly and fully below in combination with the accompanyingdrawings in the examples of the present disclosure. It is apparent thatthe described examples are merely part of examples of the presentdisclosure rather than all examples. All other examples achieved bythose of ordinary skill in the art based on the examples in the presentdisclosure without paying creative work shall fall into the scope ofprotection of the present disclosure.

FIG. 1 illustrates a flow diagram of a method of forwarding a multicastdata packet based on an example of the present disclosure. The methodmay be applied to a controlling bridge of an extended bridge. As shownin FIG. 1, the method may include the following blocks.

At block 111, a multicast data packet may be received.

At block 113, a multicast ECID and a cascade port associated with amulticast group of the multicast data packet may be determined, wherethe multicast ECID directs to egress ports in different VLANs of themulticast group on a port extender connected with the cascade port.

At block 115, an ETAG having the multicast ECID may be added to themulticast data packet.

At block 117, the multicast data packet with the ETAG having themulticast ECID may be transmitted via the cascade port.

The method of forwarding a multicast data packet shown in FIG. 1 has theadvantages that a controlling bridge may transmit one copy of multicastdata packet to a PE on which egress ports belong to one multicast groupbut different VLANs, thereby reducing the occupied bandwidth of anE-stack link.

FIG. 2 illustrates a flow diagram of a method of forwarding a multicastdata packet based on an example of the present disclosure. The methodmay be applied to a port extender of an extended bridge system. As shownin FIG. 2, the method may include the following blocks.

At block 220, a multicast data packet containing an ETAG may be receivedvia an upstream port, where a multicast ECID contained in the ETAGdirects to egress ports which belong to one multicast group butdifferent VLANs.

At block 222, multicast duplication information matching the multicastECID may be found, where the multicast duplication information containseach egress port of the multicast group corresponding to the multicastdata packet and a VLAN identification of each egress port.

At block 224, a copy of the multicast data packet may be duplicated foreach egress port based on the multicast duplication information, theETAG of each copy of the multicast data packet may be removed, and theVLAN identification of each egress port may be added to each copy of themulticast data packet, and then each copy of the multicast data packetcontaining the VLAN identification may be transmitted via each egressport.

The method of forwarding a multicast data packet shown in FIG. 2 has theadvantages that a port extender may duplicate a multicast data packetfor egress ports of different VLANs based on the multicast data packetforwarded by a controlling bridge and transmit each copy of themulticast data packet via each egress port.

In an extended bridge 300 shown in FIG. 3, a CB 31 may be connected toan upstream port 32-1 of a PE 32 and an upstream port 33-1 of a PE 33via cascade ports 31-1 and 31-2, respectively. Extended ports 32-2,32-3, 32-4 and 32-5 of the PE 32 are connected to terminals 34-37,respectively, and extended ports 33-2 and 33-3 of the PE 33 areconnected to terminals 38 and 39, respectively. The terminals 34, 35 and38 belong to a VLAN 10, and terminals 36, 37 and 39 belong to a VLAN 20.

The terminal 34 may transmit an Internet Group Management Protocol(IGMP) membership report packet for joining a multicast group G2. The PE32 may receive the IGMP membership report packet via the extended port32-2, and add an ETAG and a VLAN 10 tag to the packet, wherein the ETAGcarries a unicast ECID of the extended port 32-2. The PE 32 may transmitthe IGMP membership report packet with the ETAG and the VLAN 10 tag viathe upstream port 32-1. The CB 31 may receive the IGMP membership reportpacket containing the ETAG having the unicast ECID of the extended port32-2 and the VLAN 10 tag via the cascade port 31-1, and search for amulticast ECID and a cascade port corresponding to the multicast groupG2. If no multicast ECID associated with an egress port of the multicastgroup G2 on the PE 32 is found, a multicast ECID 3000 may be assignedfor the egress port of the multicast group G2 on the PE 32. Then, the CB31 may record the multicast ECID 3000 and the cascade port 31-1associated with the multicast group G2.

The CB 31 may identify the egress port as the extended port 32-2 basedon the unicast ECID of the extended port 32-2, and identify the VLAN 10to which the egress port belongs based on the VLAN 10 identification.The CB 31 may generate multicast duplication information (port 32-2,VLAN 10), indicating that the egress port 32-2 belongs to VLAN 10.

The CB 31 may transmit the assigned multicast ECID 3000 and thegenerated multicast duplication information to the PE 32 via the cascadeport 31-1.

The PE 32 may record that the multicast ECID 3000 is associated with thereceived multicast duplication information. For example, the PE 32 mayrecord that the multicast ECID 3000 is associated with the multicastduplication information (port 32-2, VLAN 10). For another example, thePE 32 may record a multicast duplication table index associated with themulticast ECID 3000 and record (port 32-2, VLAN 10) in the multicastduplication information that the multicast duplication table indexdirects to. The manner of recording the multicast duplicationinformation by the PE is not limited herein.

The terminals 35-37 may send IGMP membership report packets for joiningthe multicast group G2, respectively. The PE 32 may add the ETAGs andthe VLAN tags to the packets in the same manner. The PE 32 may thentransmit the IGMP membership report packets with the ETAGs and the VLANtags via the upstream port 32-1.

The CB 31 may receive these IGMP membership report packets via thecascade port 31-1 and find the multicast ECID 3000 associated with theegress port of the multicast group G2 on the PE 32. The CB 31 maygenerate a multicast duplication relationship (port 32-3, VLAN 10) and amulticast duplication relationship (port 32-4, port 32-5, VLAN 20). TheCB 31 may transmit the multicast ECID 3000 and the generated multicastduplication relationships to the PE 32.

For example, the PE 32 may further record that the multicast ECID 3000is associated with the multicast duplication relationship (port 32-2,port 32-3, VLAN 10) and the multicast duplication relationship (port32-4, port 32-5, VLAN 20) so as to record each egress port associatedwith the multicast ECID 3000 and the VLAN of each egress port. Foranother example, the PE 32 may record the multicast duplicationrelationship (port 32-2, port 32-3, VLAN 10) and the multicastduplication relationship (port 32-4, port 32-5, VLAN 20) in an egressport duplication table that the multicast duplication table indexassociated with the multicast ECID 3000 directs to.

The terminals 38 and 39 may transmit IGMP membership report packets forjoining the multicast group G2, respectively. The PE 33 may receive theIGMP membership report packets and add ETAGs having unicast ECIDs andVLAN tags into the packets, and then transmit them via the upstream port33-1.

The CB 31 may receive the IGMP membership report packets containing theETAGs having unicast ECIDs and the VLAN tags via the cascade port 31-2and assign a multicast ECID 3001 for egress ports on the PE 33 whichbelong to the multicast group G2 but different VLANs. The CB 31 maygenerate multicast duplication information (port 33-2, VLAN 10) andmulticast duplication information (port 33-3, VLAN 20). The CB 31 mayrecord the multicast ECID 3001 and the cascade port 31-2 associated withthe multicast group G2. The CB 31 may transmit the multicast ECID 3001and the generated multicast duplication information (port 33-2, VLAN 10)and (port 33-3, VLAN 20) to the PE 33 via the cascade port 31-2. The CB31 may assign one multicast ECID for the extended ports on PE 32 whichare in different VLANs but the same multicast group G2, and assign onemulticast ECID for the Extended ports on the PE 33 which are indifferent VLANs but the same multicast group G2, thereby saving theresource of the multicast ECID.

The PE 33 may record that the multicast ECID 3001 is associated with themulticast duplication relationship (port 33-2, VLAN 10) and themulticast duplication relationship (port 33-3, VLAN 20) so as to recordeach egress port associated with the multicast ECID 3001 and a VLAN towhich each egress port belongs. In an example, the PE 32 may record themulticast duplication relationship (port 33-2, VLAN 10) and (port 33-3,VLAN 20) in an egress port duplication table that a multicastduplication table index associated with the multicast ECID 3001 directsto.

As shown in FIG. 3, when receiving a multicast data packet, the CB 31may find the multicast ECID 3000 and ECID 3001 associated with themulticast group G2 based on a multicast group G2 address or a multicastsource address of the multicast data packet. The CB 31 may duplicate onecopy of the multicast data packet for all egress ports of the multicastgroup G2 on the PE 32 based on the ECID 3000, add the ETAG having theECID 3000 to the packet and transmit one copy of the multicast datapacket 3110 with the ECID 3000 via the cascade port 31-1. The CB 31 mayduplicate one copy of the multicast data packet for all egress ports ofthe multicast group G2 on the PE 33 based on the ECID 3001, add the ETAGhaving the ECID 3001 to the packet and transmit one copy of themulticast data packet 3111 with the ECID 3001 via the cascade port 31-2.The CB 31 may duplicate two copies of the multicast data packet, i.e.,one copy of the multicast data packet for the egress ports in differentVLANs of the multicast group G2 on the PE 32 and one copy of themulticast data packet for the egress ports in different VLANs of themulticast group G2 on the PE 33. Therefore, the CB 31 does not have totransmit multiple copies of multicast data packets of different VLANsfor the multicast group G2 to each PE over multiple E-stack links,thereby reducing the occupied bandwidth of the E-stack link.

The PE 32 may receive the multicast data packet 3110 carrying the ETAGvia the upstream port 32-1, and duplicate a multicast data packet foreach egress port based on multicast duplication information (port 32-2,port 32-2, VLAN 20) and (port 32-4, port 32-5, VLAN 20) matching themulticast ECID 3000 in the ETAG, and removes the ETAG of each copy ofthe multicast data packet. The PE 32 may add the VLAN 10 identificationto two copies of the multicast data packet based on the VLAN 10 of theegress ports 32-2 and 32-3 and transmit the two multicast data packetswith the VLAN 10 identification to the terminals 34 and 35 via theextended ports 32-2 and 32-3. The PE 32 may add the VLAN 20identification to another two copies of the multicast data packet basedon the VLAN 20 of the egress ports 32-4 and 32-5, respectively, andtransmit the two multicast data packets with the VLAN 20 identificationto the terminals 36 and 37 via the extended ports 32-4 and 32-5,respectively.

The PE 33 may receive a multicast data packet 3111 carrying an ETAG viathe upstream port 33-1, and duplicate the multicast data packet for eachegress port based on multicast duplication information (port 33-3, VLAN10) and (port 33-4, VLAN 20) matching with the multicast ECID 3001, andremove the ETAG of each copy of the multicast data packet. The PE 33 mayadd the VLAN 10 identification to one copy of the multicast data packetbased on the VLAN 10 of the egress port 33-2 and transmit the multicastdata packet with the VLAN 10 identification to the terminal 38 via theextended port 33-2. The PE 33 may add the VLAN 10 identification toanother copy of the multicast data packet based on the VLAN 20 of theegress port 33-3 and transmit the multicast data packet with the VLAN 20identification to the terminal 39 via the extended port 33-3.

The PE 32 and the PE 33 may respectively execute layer-3 duplicating andforwarding based on the multicast duplication information associatedwith the multicast ECID of the multicast group G2 to transmit amulticast data packet from a CB to member ports of different VLANs forthe multicast group G2.

In an extended bridge shown in FIG. 3, for example, the CB 31 may be asingle device, and may also be a stacked device constructed by stackinga plurality of devices. When the CB 31 is a stacked device, the cascadeports 31-1 and 31-2 of the CB 31 are aggregate ports including aplurality of member ports. The CB 31 may receive IGMP membership reportpackets containing unicast ECIDs and VLAN identifications transmitted bythe PE 32 and the PE 33 via upstream ports from any member port of thecascade ports 31-1 and 31-2. The CB 31 may also select any member portof the cascade ports 31-1 and 31-2 to transmit the multicast ECID, themulticast duplication information and the multicast data packet with themulticast ECID. Each of the PE 32 and the PE 33 may select one of aplurality of upstream ports connected to the CB 31 to transmit the IGMPmembership report packet containing the unicast ECID and the VLANidentification. Similarly, in the extended bridge shown in FIG. 3, forexample, other extended ports of the PE 32 and the PE 33 that are notconnected to terminals may also be connected to other PE devices.

FIG. 4 illustrates a schematic structure diagram of a device 400 forforwarding a multicast data packet based on an example of the presentdisclosure. The device 400 may be applied to a controlling bridge of anextended bridge. The device 400 for forwarding a multicast data packetmay include a receiving unit 401, a searching unit 402, a transmittingunit 403, an assigning unit 404, and a multicast duplication informationgenerating unit 405.

The receiving unit 401 is configured to receive a multicast data packet.The searching unit 402 is configured to determine a multicast E-ChannelIdentifier (ECID) and a cascade port associated with a multicast groupof the multicast data packet, where the multicast ECID directs to egressports in different VLANs of the multicast group on a port extenderconnected with the cascade port. The transmitting unit 403 is configuredto add an ETAG having the multicast ECID to the multicast data packetand transmit the multicast data packet with the ETAG having themulticast ECID via the cascade port.

The assigning unit 404 is configured to assign the multicast ECID foregress ports of different VLANs for the multicast group on the portextender. The multicast duplication information generating unit 405 isconfigured to record that the multicast group is associated with themulticast ECID and the cascade port and obtain the egress ports indifferent VLANs of the multicast group on the port extender connected tothe cascade port, and generate multicast duplication information,wherein the multicast duplication information contains a portidentification and a VLAN identification of each egress port of themulticast group. The transmitting unit 403 is further configured totransmit the multicast ECID and the multicast duplication informationvia the cascade port.

The receiving unit 401 is further configured to receive a plurality ofInternet Group Management Protocol (IGMP) membership report packets forjoining the multicast group via the cascade port, where each IGMPmembership report packet carries an ETAG and an associated VLANidentification. The multicast duplication information generating unit405 is further configured to identify each egress port based on anextended port indicated by a unicast ECID of the ETAG in each IGMPmembership report packet, and identify a VLAN to which each egress portbelongs based on the VLAN identification in each IGMP membership reportpacket.

The device 400 for forwarding a multicast data packet shown in FIG. 4may be implemented by software (for example, by machine-executableinstructions stored in a memory and run by a processor), by hardware(for example, by a processor of an Application Specific IntegratedCircuit (ASIC)), or by a combination of software and hardware.

FIG. 5 illustrates a controlling bridge provided with the device forforwarding a multicast data packet in FIG. 4 based on an example of thepresent disclosure. In FIG. 5, the controlling bridge 500 includes aforwarding unit 510, a processor 520, and a storing unit 530, a cascadeport 541 and a physical port 542 that are connected to the processor520. The forwarding unit 510 here may be, for example, a hardwareforwarding chip. The storing unit 530 may be any electronic, magnetic,optical or other physical storage device, for example, a Random AccessMemory (RAM), a volatile memory, a nonvolatile memory, a flash memory, astorage drive (e.g., hard disk drive), a solid state disk, or any typeof storage disk.

The forwarding unit 510 includes at least a receiving module 511, asearching module 512 and a transmitting module 513. The storing unit 530includes one or more encoding modules that can be run by the processor520. A plurality of encoding modules of the storing unit 530 include atleast an assigning module 531 and a multicast duplication informationgenerating module 532.

The receiving module 511 is configured to receive a multicast datapacket via the physical port 542. The searching module 512 is configuredto determine a multicast ECID and the cascade port 541 associated withmulticast group of the multicast data packet, where the multicast ECIDdirects to egress ports in different VLANs of the multicast group on aport extender connected with the cascade port 541. The transmittingmodule 513 is configured to add an ETAG having the multicast ECID to themulticast data packet and transmit the multicast data packet with theETAG having the multicast ECID via the cascade port 541.

The assigning module 531 is configured to assign the multicast ECID foregress ports in different VLANs of the multicast group on the portextender. The multicast duplication information generating module 532 isconfigured to obtain the egress ports in different VLANs of themulticast group on the port extender connected to the cascade port 541,and generate multicast duplication information, where the multicastduplication information contains a port identification and a VLANidentification of each egress port of the multicast group. Thetransmitting module 513 is further configured to transmit the multicastECID and the multicast duplication information via the cascade port 541.

The receiving module 511 is further configured to receive a plurality ofInternet Group Management Protocol (IGMP) membership report packets forjoining the multicast group via the cascade port 541, where each IGMPmembership report packet carries an ETAG and an associated VLANidentification. The multicast duplication information generating module532 is further configured to identify each egress port based on anextended port indicated by a unicast ECID of the ETAG in each IGMPmembership report packet, and identify a VLAN to which each egress portbelongs based on the VLAN identification in each IGMP membership reportpacket.

FIG. 6 illustrates a controlling bridge provided with the device forforwarding a multicast data packet in FIG. 4 based on another example ofin the present disclosure. In FIG. 6, the controlling bridge 600includes a forwarding unit 610, a processor 620, and a storing unit 630,a cascade port 641 and a physical port 642 that are connected to theprocessor 620. A plurality of encoding modules of the storing unit 630include at least a receiving module 631, a searching module 632, atransmitting module 633, an assigning module 634, and a multicastduplication information generating module 635. The forwarding unit 610here may be, for example, a hardware forwarding chip. The storing unit630 may be any electronic, magnetic, optical or other physical storagedevice, for example, a Random Access Memory (RAM), a volatile memory, anonvolatile memory, a flash memory, a storage drive (e.g., hard diskdrive), a solid state disk, or any type of storage disk.

The forwarding unit 610 is configured to receive a multicast data packetvia the physical port 642 and transmit the packet to the processor 620,and the processor 620 executes corresponding encoding modules in thestoring unit 630 to process the multicast data packet, whichspecifically includes the following operations:

The receiving module 631 is configured to receive the multicast datapacket. The searching module 632 is configured to determine themulticast ECID and the cascade port 641 associated with the multicastgroup of the multicast data packet, where the multicast ECID directs toegress ports in different VLANs of the multicast group on a portextender connected with the cascade port 641. The transmitting module633 is configured to add an ETAG having the multicast ECID to themulticast data packet and control the forwarding unit 610 to transmitthe multicast data packet with the ETAG having the multicast ECID viathe cascade port 641.

The assigning module 634 is configured to assign the multicast ECID foregress ports in different VLANs of the multicast group on the portextender. The multicast duplication information generating module 635 isconfigured to obtain the egress ports in different VLANs of themulticast group on the port extender connected to the cascade port 641,and generate multicast duplication information, where the multicastduplication information contains a port identification and a VLANidentification of each egress port of the multicast group. Thetransmitting module 633 is further configured to transmit the multicastECID and the multicast duplication information via the cascade port 641.

The receiving module 631 is further configured to receive a plurality ofIGMP membership report packets for joining the multicast group, whereeach IGMP membership report packet carries an ETAG and an associatedVLAN identification. The multicast duplication information generatingmodule 635 is configured to identify each egress port based on anextended port indicated by a unicast ECID of the ETAG in each IGMPmembership report packet, and identify a VLAN to which each egress portbelongs based on the VLAN identification in each IGMP membership reportpacket.

FIG. 7 illustrates a device 700 for forwarding a multicast data packetbased on an example of the present disclosure. The device may be appliedto a port extender of an extended bridge. The device 700 for forwardinga multicast data packet may include a receiving unit 701, a searchingunit 702 and a transmitting unit 703. The receiving unit 701 isconfigured to receive a multicast data packet containing an ETAG havinga multicast ECID via an upstream port. The searching unit 702 isconfigured to search for multicast duplication information matching themulticast ECID, where the multicast duplication information contains aport identification and a VLAN identification of each egress port of themulticast group corresponding to the multicast data packet. Thetransmitting unit 703 is configured to duplicate the multicast datapacket for each egress port based on the multicast duplicationinformation, remove the ETAG of each copy of the multicast data packet,add the VLAN identification of each egress port to each copy of themulticast data packet, and transmit the multicast data packet containingthe VLAN identification via each egress port.

The receiving unit 701 is further configured to receive IGMP membershipreport packets for joining the multicast group via extended ports. Thetransmitting unit 703 is further configured to add each IGMP membershipreport packet with an ETAG and a VLAN identification based on a unicastECID and a VLAN of each extended port receiving each IGMP membershipreport packet, and transmit each IGMP membership report packet with theETAG and the VLAN identification via the upstream port.

The receiving unit 701 is further configured to receive the multicastECID and the multicast duplication information associated with themulticast ECID which are assigned by a CB via the upstream port. Thesearching unit 702 is further configured to record the receivedmulticast ECID and the multicast duplication information.

The device 700 for forwarding a multicast data packet shown in FIG. 7may be implemented by software (for example, by machine-executableinstructions stored on a memory and run by a processor), by hardware(for example, by a processor of an Application Specific IntegratedCircuit (ASIC)), or by a combination of software and hardware.

FIG. 8 illustrates a port extender provided with the device forforwarding a multicast data packet in FIG. 7 based on an example of thepresent disclosure. In FIG. 8, the controlling bridge 800 includes aforwarding unit 810, a processor 820, and a storing unit 830, aplurality of extended ports 841 and an upstream port 842 that areconnected to the processor 820. The forwarding unit 810 includes atleast a receiving module 811, a searching module 812, and a transmittingmodule 813. The forwarding unit 810 here may be, for example, a hardwareforwarding chip. The storing unit 830 may be any electronic, magnetic,optical or other physical storage device, for example, a Random AccessMemory (RAM), a volatile memory, a nonvolatile memory, a flash memory, astorage drive (e.g., hard disk drive), a solid state disk, or any typeof storage disk.

The receiving module 811 is configured to receive a multicast datapacket containing an ETAG having a multicast ECID via the upstream port842. The searching module 812 is configured to search for multicastduplication information matching the multicast ECID, where the multicastduplication information contains a port identification and a VLANidentification of each egress port of the multicast group correspondingto the multicast data packet. The transmitting module 813 is configuredto duplicate the multicast data packet for each egress port based on themulticast duplication information, remove the ETAG of each copy of themulticast data packet, add the VLAN identification of each egress portto each copy of the multicast data packet, and transmit the multicastdata packet containing the VLAN identification via each egress port.

The receiving module 811 is further configured to receive IGMPmembership report packets for joining the multicast group via theextended ports 841. The transmitting module 813 is configured to addeach IGMP membership report packet with an ETAG and a VLANidentification based on a unicast ECID and a VLAN of each extended portreceiving each IGMP membership report packet, and transmit each IGMPmembership report packet with the ETAG and the VLAN identification viathe upstream port 842.

The receiving module 811 is further configured to receive the multicastECID and the multicast duplication information associated with themulticast ECID which are assigned by a CB. The searching module 812 isfurther configured to record the received multicast ECID and themulticast duplication information.

FIG. 9 illustrates a port extender provided with the device forforwarding a multicast data packet in FIG. 7 based on another example ofthe present disclosure. In FIG. 9, the controlling bridge 900 includes aforwarding unit 910, a processor 920, and a storing unit 930, aplurality of extended ports 941 and an upstream port 942 that areconnected to the processor 920. A plurality of encoding modules of thestoring unit 930 include at least a receiving module 931, a searchingmodule 932, and a transmitting module 933. The forwarding unit 910 heremay be, for example, a hardware forwarding chip. The storing unit 930may be any electronic, magnetic, optical or other physical storagedevice, for example, a Random Access Memory (RAM), a volatile memory, anonvolatile memory, a flash memory, a storage drive (e.g., hard diskdrive), a solid state disk, or any type of storage disk.

The forwarding unit 910 is configured to receive a multicast data packetcontaining an ETAG having an ECID via the upstream port 942 and transmitthe packet to the processor 920, and the processor 920 executescorresponding encoding modules in the storing unit 930 to process themulticast data packet, which specifically includes the followingoperations:

The receiving module 931 is configured to receive the multicast datapacket. The searching module 932 is configured to search for multicastduplication information matching the multicast ECID, where the multicastduplication information contains a port identification and a VLANidentification of each egress port of the multicast group correspondingto the multicast data packet. The transmitting module 933 is configuredto duplicate the multicast data packet for each egress port based on themulticast duplication information, remove the ETAG of each copy of themulticast data packet, add the VLAN identification of each egress portto each copy of the multicast data packet, and transmit the multicastdata packet containing the VLAN identification via each egress port.

The receiving module 931 is further configured to receive IGMPmembership report packets for joining the multicast group. Thetransmitting module 933 is further configured to add each IGMPmembership report packet with an ETAG and a VLAN identification based ona unicast ECID and a VLAN of each extended port receiving each IGMPmembership report packet and control the forwarding unit 910 to transmiteach IGMP membership report packet with the ETAG and the VLANidentification via the upstream port 942.

The receiving module 931 is further configured to receive the multicastECID and the multicast duplication information associated with themulticast ECID which are assigned by a controlling bridge. The searchingmodule 932 is configured to record the received multicast ECID and themulticast duplication information.

Since the device examples substantially correspond to the methodexamples, a reference may be made to part of the descriptions of themethod examples for the related part. The device examples describedabove are merely illustrative, where the units described as separatemembers may be or not be physically separated, and the members displayedas units may be or not be physical units, i.e., may be located in oneplace, or may be distributed to a plurality of network units. Part orall of the modules may be selected based on actual requirements toimplement the objectives of the solutions in the examples. Those ofordinary skill in the art may understand and carry out them withoutcreative work.

It shall be noted that the relational terms such as “first” and “second”used herein are merely intended to distinguish one entity or operationfrom another entity or operation rather than to require or imply anysuch actual relation or order existing between these entities oroperations. Also, the term “including”, “containing” or any variationthereof is intended to encompass non-exclusive inclusion, so that aprocess, method, article or device including a series of elementsincludes not only those elements but also other elements not listedexplicitly or those elements inherent to such a process, method, articleor device. Without more limitations, an element defined by the statement“including a . . . ” shall not be precluded to include additional sameelements present in a process, method, article or device including theelements.

The above are detailed description of a method and a device providedbased on the examples of the present disclosure. Specific examples areused herein to set forth the principles and the implementing methods ofthe present disclosure, and the descriptions of the above examples areonly meant to help understanding of the method and the core idea of thepresent disclosure. Meanwhile, those of ordinary skill in the art maymake alterations to the specific examples and the scope of applicationin accordance with the idea of the present disclosure. In conclusion,the contents of the present specification shall not be interpreted aslimiting to the present disclosure.

The invention claimed is:
 1. A method of forwarding a multicast datapacket, comprising: receiving, by a controlling bridge, a multicast datapacket; determining, by the controlling bridge, a multicast E-ChannelIdentification (ECID) and a cascade port associated with a multicastgroup of the multicast data packet, wherein the multicast ECID directsto egress ports in different VLANs of the multicast group on a portextender connected with the cascade port; adding, by the controllingbridge, an Extension VLAN Tag (ETAG) having the multicast ECID to themulticast data packet; and transmitting, by the controlling bridge, themulticast data packet with the ETAG having the multicast ECID via thecascade port.
 2. The method according to claim 1, wherein beforereceiving the multicast data packet, the method comprises: obtaining, bythe controlling bridge, egress ports in different VLANs of the multicastgroup on the port extender connected with the cascade port; assigning,by the controlling bridge, the multicast ECID for the egress ports indifferent VLANs of the multicast group on the port extender; recording,by the controlling bridge, that the multicast group is associated withthe multicast ECID and the cascade port; generating, by the controllingbridge, multicast duplication information, wherein the multicastduplication information contains a port identification and a VLANidentification of each egress port of the multicast group on the portextender; and transmitting, by the controlling bridge, the multicastECID and the multicast duplication information to the port extender viathe cascade port.
 3. The method according to claim 2, wherein obtainingthe egress ports in different VLANs of the multicast group on the portextender connected with the cascade port comprises: receiving, by thecontrolling bridge, a plurality of Internet Group Management Protocol(IGMP) membership report packets containing VLAN identifications andETAGs and for joining the multicast group, via the cascade port;identifying, by the controlling bridge, each egress port based on anextended port indicated by a unicast ECID of the ETAG in each IGMPmembership report packet; and identifying, by the controlling bridge, aVLAN to which each egress port belongs based on the VLAN identificationin each IGMP membership report packet.
 4. A device for forwarding amulticast data packet, which is applied to a controlling bridge of anextended bridge, and the device comprising: a receiving unit configuredto receive a multicast data packet; a searching unit configured todetermine a multicast E-Channel Identification (ECID) and a cascade portassociated with a multicast group of the multicast data packet, whereinthe multicast ECID directs to egress ports in different VLANs of themulticast group on a port extender connected with the cascade port; anda transmitting unit configured to add an Extension VLAN Tag (ETAG)having the multicast ECID to the multicast data packet and transmit themulticast data packet with the ETAG having the multicast ECID via thecascade port.
 5. The device according to claim 4, further comprising: anassigning unit configured to assign the multicast ECID for egress portsin different VLANs of the multicast group on the port extender; and amulticast duplication information generating unit configured to recordthat the multicast group is associated with the multicast ECID and thecascade port, obtain the egress ports in different VLANs of themulticast group on the port extender connected with the cascade port,and generate multicast duplication information, wherein the multicastduplication information contains a port identification and a VLANidentification of each egress port of the multicast group on the portextender; and a transmitting unit configured to transmit the multicastECID and the multicast duplication information to the port extender viathe cascade port.
 6. The device according to claim 5, wherein thereceiving unit is configured to receive a plurality of Internet GroupManagement Protocol (IGMP) membership report packets containing VLANidentifications and ETAGs and for joining the multicast group, via thecascade port; and the multicast duplication information generating unitis configured to identify each egress port based on an extended portindicated by a unicast ECID of the ETAG in each IGMP membership reportpacket, and identify a VLAN to which each egress port belongs based onthe VLAN identification in each IGMP membership report packet.
 7. Adevice for forwarding a multicast data packet, which is applied to aport extender of an extended bridge system, and the device comprising: areceiving unit configured to receive a multicast data packet containingan Extension VLAN Tag (ETAG) having a multicast E-Channel Identification(ECID) via an upstream port; a searching unit configured to search formulticast duplication information matching the multicast ECID, whereinthe multicast duplication information contains a port identification anda VLAN identification of each egress port of a multicast groupcorresponding to the multicast data packet; and a transmitting unitconfigured to duplicate the multicast data packet for each egress portbased on the multicast duplication information, remove the ETAG of eachcopy of the multicast data packet, add the VLAN identification of eachegress port to each copy of the multicast data packet, and transmit themulticast data packet containing the VLAN identification via each egressport.
 8. The device according to claim 7, wherein the receiving unit isconfigured to receive a plurality of Internet Group Management Protocol(IGMP) membership report packets for joining the multicast group via aplurality of extended ports, respectively; and the transmitting unit isconfigured to add an ETAG and a VLAN identification to each IGMPmembership report packet based on a unicast ECID and a VLAN of eachextended port receiving each IGMP membership report packet, and transmiteach IGMP membership report packet with the ETAG and the VLANidentification via the upstream port.
 9. The device according to claim8, wherein the receiving unit is configured to receive, via the upstreamport, multicast ECID and multicast duplication information associatedwith the multicast ECID which are assigned by a controlling bridge inthe extended bridge system; and the searching unit is configured torecord the received multicast ECID and multicast duplicationinformation.
 10. An extended bridge system comprising a controllingbridge and a plurality of port extenders, wherein the controlling bridgecomprises the device as claimed in claim 4; and one of the portextenders is configured to: receive a multicast data packet with theETAG having the multicast ECID via an upstream port connected with thecascade port; search for multicast duplication information matching themulticast ECID, wherein the multicast duplication information contains aport identification and a VLAN identification of each egress port of themulticast group; duplicate the multicast data packet for each egressport based on the multicast duplication information, remove the ETAG ofeach copy of the multicast data packet, add the VLAN identification ofeach egress port to each copy of the multicast data packet, and transmiteach copy of the multicast data packet containing the VLANidentification via each egress port.
 11. A method of forwarding amulticast data packet, executed by the device as claimed in claim 7,comprising: receiving a multicast data packet containing an ExtensionVLAN Tag (ETAG) having a multicast E-Channel Identification (ECID) viaan upstream port; searching for multicast duplication informationmatching the multicast ECID, wherein the multicast duplicationinformation contains a port identification and a VLAN identification ofeach egress port of a multicast group corresponding to the multicastdata packet; and duplicating the multicast data packet for each egressport based on the multicast duplication information, removing the ETAGof each copy of the multicast data packet, adding the VLANidentification of each egress port to each copy of the multicast datapacket, and transmitting the multicast data packet containing the VLANidentification via each egress port.
 12. The method according to claim11, wherein before receiving the multicast data packet containing theETAG having the multicast ECID via the upstream port, the methodcomprises: receiving a plurality of Internet Group Management Protocol(IGMP) membership report packets for joining the multicast group via aplurality of extended ports, respectively; adding an ETAG and a VLANidentification to each IGMP membership report packet based on a unicastECID and a VLAN of an extended port receiving each IGMP membershipreport packet; and transmitting each IGMP membership report packet withthe ETAG and the VLAN identification via the upstream port.
 13. Themethod according to claim 12, wherein before receiving the multicastdata packet containing the ETAG having the multicast ECID via theupstream port, the method comprises: receiving the multicast ECID andthe multicast duplication information associated with the multicast ECIDwhich are assigned by a controlling bridge via the upstream port; andrecording the received multicast ECID and multicast duplicationinformation.